home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Sun Solutions 2000 #2
/
Sun Solutions CD (Volume 2 2000)(Special Focus - Java Technologies)(Disc 1).ISO
/
products
/
Software
/
BostonBusinessComputing
/
bbc
/
README.EDT+
< prev
next >
Wrap
Text File
|
2000-02-11
|
7KB
|
182 lines
README
======
EDT+ version 7.32
Copyright 1985-1999 Boston Business Computing, Ltd.
1. Introduction
===============
Thank you for selecting EDT+ from Boston Business Computing, Ltd.
This file contains the following sections:
1. Introduction
2. Installation
3. Technical Support
4. EDT+ and UNIX Window Systems
5. Startup Command Files
6. Known Problems and Limitations
The documentation for EDT+ consists of the "EDT+ Reference Guide", the
"Installation and Troubleshooting" booklet, the online EDT+ help library,
and the online UNIX man page.
The ID.EDT+ file describes all files in the EDT+ release.
2. Installation
===============
Please refer to the "Installation and Troubleshooting" booklet.
3. Technical Support
====================
Purchasing EDT+ entitles you to sixty days of free phone support via our
Technical Support Line. The support line can be reached at (978)
725-3222. Hours are 9:00-5:00 (Eastern) Monday through Friday. Please
have your product serial number or maintenance authorization number
available when you call. If you prefer, you may communicate problems,
questions, or enhancement requests via FAX (send to EDT+ Support at (978)
725-3229) or email (sales@bosbc.com). We make every effort to respond to
queries from supported customers within two business days.
Extended support can be purchased for an additional charge. Extended
support entitles you to access to the Technical Support Line, priority
bug fixes and free maintenance updates during the term of the support
period. Please contact our sales department for pricing.
Customers who are not on support may communicate problems, questions or
enhancement requests via FAX or email (see above).
4. EDT+ and UNIX Window Systems
===============================
When EDT+ runs in a UNIX windows environment it will usually open an
`xterm' window with the application name "bbc". This window uses the
file /usr/lib/bbc/xdefaults to define the keypad similarly to a DEC
vt-style terminal. Without this xdefaults file we do not guarantee that
the keypad will be mapped correctly. The following situations will cause
EDT+ to display in the current window, ignoring the settings in the
xdefaults file:
1. Use the program `bbcxterm' as your default command shell window.
`bbcxterm' starts your standard `xterm' program with keys
redefined similarly to a vt100.
2. Set the environment variable "BBCNOX" to 1
3. Unset the DISPLAY environment variable
4. Invoke EDT+ as `edt -nodisplay'
It is possible that some keys on your keypad will be defined by the
window manager, making it impossible for EDT+ to redefine them. For
instance, you may find that the KEYPAD key minimizes the EDT+ window
instead of moving to the next line. In this situation it will be
necessary to investigate your window manager documentation for
instructions on redefining that key.
If you experience problems with the Num Lock key such as it having no
effect or toggling the keypad into numeric mode, then this is probably a
result of interference from the window manager. In this case, the
function keys F1 - F4 function keys keys should be used as alternatives
to the four keys on the top of the numeric keypad. The `edtcode' program
can be used to determine specific key assignments.
The program `/usr/lib/bbc/fixnumlock' can also be used to change the
behavior of Num Lock under many X Window managers. This program will
clear the "special" meaning of Num Lock and allow it to be used as a
normal key by EDT+. Be advised that, although the Num Lock light may
still operate, it is likely that the Num Lock will not toggle the
behavior of your keypad after running this program.
5. Startup Command Files
========================
The system-wide startup command file for EDT+ is /usr/lib/bbc/edtini.edt.
This file contains EDT+ line-mode commands that configure various aspects
of EDT+. The last line in this file is:
set command ~/edtini.edt
This command directs EDT+ to read the edtini.edt file in the user's home
directory. This allows each user to configure their own editing session
without affecting the other users on the system. Please note that this
*must* be the last line in the system wide initialization file. Any
commands entered beyond this command will be ignored.
*Important*: Do not copy the system wide initialization file to
your home directory. If the file edtini.edt does not exist in your
home directory, you must create it. If you copy the system wide
initialization file to your home directory, EDT+ will execute an
infinite loop when beginning an editing session.
We have also included with this release a file called edtcmnd.new. This
file is located in the BBC library directory and contains advanced key
definitions that can be made part of a user's session with EDT+ by just
including them into their own edtini.edt file. The edtcmnd.new file
contains key definitions for the following:
GOLD W
open an new window
GOLD B
open a window to a specified buffer input by the user
GOLD O
move to other window
GOLD CTRL O
close inactive window
GOLD A
repeat last edit
GOLD U
undo previous deletions
GOLD C
cancel the undo
GOLD G
switch to specified buffer
GOLD E
edit a file in a buffer by the same name
CTRL N
edit the next file in the queue
CTRL P
edit previous file in the queue
GOLD S
substitute first entry with second entry
GOLD N
substitute next
GOLD CTRL E
edit a new file into a buffer, and open a window to display it
GOLD R
shell out to operating system and run a program input by the user
You may want to modify some of these definitions to perform additional
functions to suit your needs.
6. Known Problems and Limitations
=================================
Redirecting the output of `edtcode' to a file as mentioned in the EDT+
manual produces a zero-length file when edtcode is invoked in an
X-Windows environment. `edtcode' behaves correctly otherwise.